Skip to content

fix: 🐛 Unable to call unlock in a module in use#240

Merged
remimd merged 1 commit intodevfrom
fix
May 15, 2025
Merged

fix: 🐛 Unable to call unlock in a module in use#240
remimd merged 1 commit intodevfrom
fix

Conversation

@remimd
Copy link
Copy Markdown
Member

@remimd remimd commented May 15, 2025

No description provided.

@remimd remimd requested a review from Copilot May 15, 2025 09:15
@remimd remimd self-assigned this May 15, 2025
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes an issue where calling unlock on a module in use did not behave as expected. Key changes include adding a new test for raising a ModuleLockError when unlocking a module in use and modifying the unlock method to dispatch an UnlockCalled event with a lock_bypass flag.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
tests/core/test_module.py Adds a test case to ensure ModuleLockError is raised when unlocking a module that is in use.
injection/_core/module.py Updates the unlock method to dispatch an UnlockCalled event with lock_bypass and modifies the dispatch flow.

Comment thread injection/_core/module.py
@remimd remimd merged commit 9f04005 into dev May 15, 2025
5 checks passed
@remimd remimd deleted the fix branch May 15, 2025 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants